Nice!
The '<2' limit for pydantic version won't work as Fedora only have v2.
Do you know why epel9 was never updated to v2?

What do you think about this settings for BaseModel?
https://docs.astral.sh/ruff/settings/#lint_flake8-type-checking_runtime-evaluated-base-classes

I updated Pydantic to v2, but I'm not sure how to make it work on EPEL 9, which only supports v1.

Since Pydantic v2 supports backward compatibility with v1 through pydantic.v1, I downgraded to v1 and added Pydantic to tmt._compat. I'm not sure if this is the best solution, but it should work with both versions and ensure that we only use features from v1.

What do you think about this settings for BaseModel?
https://docs.astral.sh/ruff/settings/#lint_flake8-type-checking_runtime-evaluated-base-classes

It may be a good idea to add that. I didn't encounter any problems without it, but it may be needed in some scenarios. Added in 9481860

As this is a new approach, it would be good to get a few more reviews. Moving to 1.40.

I followed the extended test ,and put the following ~/.config/link.fmf:

issue-tracker:
  - type: jira
    url: https://issues.redhat.com
    tmt-web-url: http://tmt.testing-farm.io/
    unkown: value

Then run tmt link command, got no warning, I guess we could warn users by printing the str(error.cause),
similar as how your test works? @therazix

I followed the extended test ,and put the following ~/.config/link.fmf:

issue-tracker:
  - type: jira
    url: https://issues.redhat.com
    tmt-web-url: http://tmt.testing-farm.io/
    unkown: value

Then run tmt link command, got no warning, I guess we could warn users by printing the str(error.cause), similar as how your test works? @therazix

You are right, thanks for the review. The issue was that SpecificationError was caught by except tmt.utils.MetadataError, so no exception was raised. It should be fixed in 0b7cd2b.

It should be fixed in 0b7cd2b.

Confirmed.

Rawhide failure irrelevant, merging.